trigger new object creation

johnzweck - Wed May 12 11:25:10 EDT 2010

Create triggers work only on discussions and comments. Use a sync trigger similar to:

trigger("New Object Trigger", module->object, post, sync, 10, "print identifier(current Object) \"\\n\"")

 

This actually looks at all objects, but you can put a check in your DXL file to see if it's a new Object. Using this as a post sync ensures that the current Object is the new Object.

John

 

johnzweck - Wed May 12 11:25:10 EDT 2010

Create triggers work only on discussions and comments. Use a sync trigger similar to:

trigger("New Object Trigger", module->object, post, sync, 10, "print identifier(current Object) \"\\n\"")

 

This actually looks at all objects, but you can put a check in your DXL file to see if it's a new Object. Using this as a post sync ensures that the current Object is the new Object.

John

 

Trigger T = current Trigger
Object o = object T
 
Date cr = o."Created On"
 
int curTime = intOf(dateAndTime(today)) //current time in seconds
int creTime = intOf(dateAndTime(cr))    //object creation time in seconds
 
creTime = creTime + 1 //increase object creation time by 1 sec
 
//if object was created in the last sec then...
if(curTime < creTime) then {
 /****** whatever code you want ******/
}

johnzweck - Wed May 12 11:25:10 EDT 2010

Create triggers work only on discussions and comments. Use a sync trigger similar to:

trigger("New Object Trigger", module->object, post, sync, 10, "print identifier(current Object) \"\\n\"")

 

This actually looks at all objects, but you can put a check in your DXL file to see if it's a new Object. Using this as a post sync ensures that the current Object is the new Object.

John

 

llandale - Thu May 13 15:22:04 EDT 2010

This is over my head, but perhaps we can modify the 'create' object functions by inserting our own in the user's Top context. Such code would look something like this:

Object createOriginal(Object obj)
{  return(create(obj))      // issue call to the original create
}    // end createOriginal()
Object create(Object obj)
{      // Enhanced, replaces original create
   Object oCreated = createOriginal(obj)
   if (null oCreated) return(oCreated)
        // now deal with the newly created object 'oCreated' as you see fit
 
   return(oCreated)
}   // end enhanced create(Object)

Sadly, there 9 'create' Object functions that all must be Enhanced.

And then there's the problem of copy-pasted objects, but perhaps they use these 'create' functions.

And then there's the problem of inserting this code into the User's top context. Perhaps that can be done with a post-module-open trigger, that cleverly uses eval_ to determine if function 'createOriginal' exists, and if not then issues evalTop_ to insert the code.

One should write this code as carefully as one would light a BBQ fire, while holding a leaky baggy of gasolene over your head.

Look forward to Mathias' input here. This is new territory. Perhaps he can become the 'Columbus of DXL Enhancement', ignoring contributions by previous Lief Ericsons.

 

 

• Louie

 

 

Mathias Mamsch - Thu May 13 15:52:37 EDT 2010
Sorry Louie to disappoint you there, but I will not get on a boat for this one :-) Hooking create on the top level will do for all DXL scripts you could easily do that on the startup script of the client, but this has no effect on the module editor. The problem is that object creation by pressing "Insert" or Copy/Pasting objects is rooted deep in the DOORS client outside the scope of DXL. This gets obvious, when you think about the fact that copying an object will copy even attribute values that you have no access to (which is a great way of identifying copied objects by the way). Modifying the DOORS client to do this might be possible but is probably generally a bad idea.

What works decently is a "pre save" trigger on the module, that will scan for objects that have been created in this session (check the DOORS history!) and perform some action, maybe combined with the sync trigger that will fire only unreliably and remember the user to do stuff.

I find that people want to implement those "object creation" triggers because they want to fill out an attribute, present a dialog box to "force" the user to do something or some other reason. In 95% of the cases there is probably a more DOORS like way to do the same thing, but iannacones did not tell us what the reason for the object creation trigger is, so I cannot help with this one.

Regards, Mathias

---

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS